<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Monitoring overview | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'monitoring-overview.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/monitoring-overview.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/monitoring-overview.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/monitoring-overview.html" rel="nofollow" target="_blank">../en/monitoring-overview.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="monitor-elasticsearch-cluster.html">Monitor a cluster</a></span>
»
<span class="breadcrumb-node">Monitoring overview</span>
</div>
<div class="navheader">
<span class="prev">
<a href="monitor-elasticsearch-cluster.html">« Monitor a cluster</a>
</span>
<span class="next">
<a href="how-monitoring-works.html">How monitoring works »</a>
</span>
</div>
<div class="chapter xpack">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="monitoring-overview"></a>Monitoring overview<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/monitoring/overview.asciidoc">edit</a><a class="xpack_tag" href="https://www.elastic.co/subscriptions"></a>
</h2>
</div></div></div>

<p>When you monitor a cluster, you collect data from the Elasticsearch nodes, Logstash nodes,
Kibana instances, and Beats in your cluster. You can also
<a class="xref" href="configuring-filebeat.html" title="Collecting Elasticsearch log data with Filebeat">use Filebeat to collect Elasticsearch logs</a>.</p>
<p>All of the monitoring metrics are stored in Elasticsearch, which enables you to easily
visualize the data from Kibana. By default, the monitoring metrics are stored in
local indices.</p>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>In production, we strongly recommend using a separate monitoring cluster.
Using a separate monitoring cluster prevents production cluster outages from
impacting your ability to access your monitoring data. It also prevents
monitoring activities from impacting the performance of your production cluster.
For the same reason, we also recommend using a separate Kibana instance for
viewing the monitoring data.</p>
</div>
</div>
<p>You can use Metricbeat to collect and ship data about Elasticsearch, Kibana, Logstash, and
Beats directly to your monitoring cluster rather than routing it through your
production cluster. The following diagram illustrates a typical monitoring
architecture with separate production and monitoring clusters:</p>
<div class="imageblock">
<div class="content">
<img src="../static/images/architecture.png" alt="A typical monitoring environment">
</div>
</div>
<p>If you have the appropriate license, you can route data from multiple production
clusters to a single monitoring cluster. For more information about the
differences between various subscription levels, see:
<a href="https://www.elastic.co/subscriptions" class="ulink" target="_top">https://www.elastic.co/subscriptions</a></p>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>In general, the monitoring cluster and the clusters being monitored
should be running the same version of the stack. A monitoring cluster cannot
monitor production clusters running newer versions of the stack. If necessary,
the monitoring cluster can monitor production clusters running the latest
release of the previous major version.</p>
</div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="monitor-elasticsearch-cluster.html">« Monitor a cluster</a>
</span>
<span class="next">
<a href="how-monitoring-works.html">How monitoring works »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>